| Auto Pass |
0 |
NIEM-2.1_5-01: XML
Schema Conformance |
The schema MUST conform to XML
as specified by [XML]. |
| Auto Pass |
0 |
NIEM-2.1_5-02_REF_SUB_EXT_CON: |
The schema MUST conform to the
specification for namespaces in XML, as defined by [XMLNamespaces] and
[XMLNamespacesErrata]. |
| Auto Pass |
0 |
NIEM-2.1_5-03_REF_SUB_EXT_CON: |
The schema MUST conform to the
W3C XML Schema Recommendations: XML Schema Part 1: Structures and XML
Schema Part 2: Datatypes, as specified by [XMLSchemaStructures] and
[XMLSchemaDatatypes]. |
| Manual Fail |
0 |
NIEM-2.1_5-04_REF_EXT: |
Within a NIEM-conformant schema,
the data definition provided for each documented component SHALL follow
the requirements and recommendations for data definitions given by [ISO
11179 Part 4]. |
| Manual Fail |
0 |
NIEM-2.1_5-05_REF_SUB_EXT: |
A NIEM component name SHALL be
formed by applying the informative guidelines and examples detailed in
Annex A of [ISO 11179 Part 5], with exceptions as specified in this
document, most notably those specified in Section 9, Naming Rules. |
| Auto Pass |
0 |
NIEM-2.1_6-01_REF_SUB_EXT: Complex
Types may not have Mixed Content |
Within the schema, an element
xsd:complexType SHALL NOT own the attribute mixed with the value true.
|
| Auto Pass |
0 |
NIEM-2.1_6-02_REF_SUB_EXT: Element
Declarations may not have Mixed Content |
Within the schema, an element
declaration that is of complex content SHALL NOT own the attribute mixed
with the value true |
| Auto Pass |
0 |
NIEM-2.1_6-03_REF_SUB_EXT: No
reference to xsd:NOTATION. |
The schema SHALL NOT contain a
reference to the type definition xsd:NOTATION or to a type derived from
that type. |
| Auto Pass |
0 |
NIEM-2.1_6-04_REF_SUB_EXT: No use of
xsd:notation. |
The schema SHALL NOT contain the
element xsd:notation. |
| Auto Pass |
0 |
NIEM-2.1_6-05_REF_SUB_EXT: No use of
xsd:include. |
The schema SHALL NOT contain the
element xsd:include. |
| Auto Pass |
0 |
NIEM-2.1_6-06_REF_SUB_EXT: No use of
xsd:redefine. |
The schema SHALL NOT contain the
element xsd:redefine. |
| Auto Pass |
0 |
NIEM-2.1_6-07_REF_SUB_EXT: No use of
xsd:anyType. |
The schema SHALL NOT reference
the type xsd:anyType. |
| Manual Fail |
0 |
NIEM-2.1_6-08_REF_SUB_EXT: No
unconstrained type substition - anySimpleType. |
The schema SHALL NOT reference
the type xsd:anySimpleType. |
| Auto Pass |
0 |
NIEM-2.1_6-09_REF_SUB_EXT: Untyped
elements must be abstract. |
Within the schema, an element
declaration with the attribute name and without the attribute type MUST
carry the attribute abstract with the value true. |
| Auto Pass |
0 |
NIEM-2.1_6-10_REF_SUB_EXT: No untyped
attributes. |
Within the schema, an attribute
declaration with attribute name MUST carry the attribute type. |
| Auto Pass |
0 |
NIEM-2.1_6-11_REF_SUB: No use of
xsd:any. |
The schema SHALL NOT contain the
element xsd:any. |
| Auto Pass |
0 |
NIEM-2.1_6-12_REF_SUB_EXT: No use of
xsd:anyAttribute. |
The schema SHALL NOT contain the
element xsd:anyAttribute. |
| Auto Pass |
0 |
NIEM-2.1_6-13_REF_SUB_EXT: No
anonymous types. |
Within the schema, any
occurrence of the element xsd:complexType or xsd:simpleType MUST appear as
an immediate child of the element xsd:schema. |
| Auto Pass |
0 |
NIEM-2.1_6-14_REF_SUB_EXT: No local
element declarations. |
Within the schema, any element
declaration carrying the attribute name MUST appear as an immediate child
of the document element xsd:schema. |
| Auto Pass |
0 |
NIEM-2.1_6-15_REF_SUB_EXT: No local
attribute declarations. |
Within the schema, any attribute
declaration owning the attribute name MUST appear as an immediate child of
the document element xsd:schema. |
| Auto Pass |
0 |
NIEM-2.1_6-16_REF_EXT: No uniqueness
constraints. |
The schema SHALL NOT contain any
of the elements xsd:unique, xsd:key, xsd:keyref, xsd:selector, or
xsd:field. |
| Auto Pass |
0 |
NIEM-2.1_6-17_REF_SUB_EXT: No use of
all or choice. |
The schema SHALL NOT contain the
element xsd:all. |
| Auto Pass |
0 |
NIEM-2.1_6-18_REF:
No use of all or choice. |
The schema SHALL NOT contain the
element xsd:choice. |
| Auto Pass |
0 |
NIEM-2.1_6-19_REF_SUB: child of
xsd:sequence must be annotation or element. |
Within the schema, any immediate
child of a model group xsd:sequence element MUST be one of xsd:annotation
or xsd:element. |
| Auto Pass |
0 |
NIEM-2.1_6-20_EXT:
No recursively defined model groups - xsd:sequence |
Within the schema, any immediate
child of a model group xsd:sequence element MUST be one of xsd:annotation,
xsd:element, xsd:choice, or xsd:any. |
| Auto Pass |
0 |
NIEM-2.1_6-21_EXT:
No recursively defined model groups - xsd:choice. |
Within the schema, any immediate
child of a model group xsd:choice element MUST be one of xsd:annotation or
xsd:element. |
| Manual Fail |
0 |
NIEM-2.1_6-22_EXT:
No recursively defined model groups - xsd:choice. |
The use of xsd:choice SHALL
define syntax, structure, grouping, and cardinality of instances, but
SHALL NOT define semantics. The semantics of a property within an
xsd:choice SHALL be identical to the semantics of the property within an
xsd:sequence. |
| Auto Pass |
0 |
NIEM-2.1_6-23_REF_SUB_EXT: No use of
xsd:group |
The schema SHALL NOT contain the
element xsd:group. |
| Auto Pass |
0 |
NIEM-2.1_6-24_REF_SUB_EXT: Sequence
minoccurs can only be 1. |
Within the schema, if the
element xsd:sequence carries the attribute minOccurs, it MUST set the
value for the attribute to 1. |
| Auto Pass |
0 |
NIEM-2.1_6-25_REF_SUB_EXT: Sequence
maxOccurs can only be 1. |
Within the schema, if the
element xsd:sequence carries the attribute maxOccurs, it MUST set the
value of the attribute to 1. |
| Auto Pass |
0 |
NIEM-2.1_6-26_REF_EXT: No blocking in
element declaration. |
Within the schema, if an element
declaration carries the attribute block, it MUST set the value for the
attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-27_REF_EXT: No blocking in
element declaration. |
Within the schema, if a complex
type definition carries the attribute block, it MUST set the value for the
attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-28_REF_SUB_EXT: No
blocking as schema default. |
Within the schema, if the
document element xsd:schema carries the attribute blockDefault, it MUST
set the value for the attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-29_REF_SUB: No final in a
simple type definition. |
Within the schema, if a simple
type definition carries the attribute final, it MUST set the value for the
attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-30_REF_SUB: No final in a
complex type definition. |
Within the schema, if a complex
type definition carries the attribute final, it MUST set the value for the
attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-31_REF_SUB: No final in an
element declaration. |
Within the schema, if an element
declaration carries the attribute final, it MUST set the value for the
attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-32_REF_SUB_EXT: No final
as schema default. |
Within the schema, if the
document element xsd:schema carries the attribute finalDefault, it MUST
set the value for that attribute to the empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-33_REF_SUB_EXT_CON: No
default in elements. |
Within the schema, any element
xsd:element SHALL NOT carry the attribute default. |
| Auto Pass |
0 |
NIEM-2.1_6-34_REF_SUB_EXT_CON: No
default in attributes. |
Within the schema, any element
xsd:attribute SHALL NOT carry the attribute default. |
| Auto Pass |
0 |
NIEM-2.1_6-35_REF_SUB_EXT_CON:
Schema must have target namespace. |
Within the schema, the document
element xsd:schema MUST carry the attribute targetNamespace. |
| Auto Pass |
0 |
NIEM-2.1_6-36_REF_SUB_EXT_CON:
Schema element targetName must be an absolute URI. |
Within the schema, the value of
the required attribute targetNamespace on the document element xsd:schema
MUST match the production <absolute-URI> as defined by [RFC3986].
|
| Auto Pass |
0 |
NIEM-2.1_6-37_REF_SUB_EXT_CON:
xsd:schema must have version attribute. |
Within the schema, the document
element xsd:schema MUST carry the attribute version. |
| Auto Pass |
0 |
NIEM-2.1_6-38_REF_SUB_EXT_CON:
xsd:schema version attribute cannot be empty. |
Within the schema, the value of
the required attribute version on the document element xsd:schema MUST NOT
be an empty string. |
| Auto Pass |
0 |
NIEM-2.1_6-39_REF_SUB_EXT_CON:
xsd:import attribute namespace required. |
Within the schema, the element
xsd:import MUST carry the attribute namespace. |
| Auto Pass |
0 |
NIEM-2.1_6-40_REF_SUB_EXT: xsd:import
namespace must be an absolute URI as defined by [RFC3986]. |
Within the schema, the value of
the required attribute namespace owned by the element xsd:import MUST
match the production <absolute-URI> as defined by [RFC3986]. |
| Auto Pass |
0 |
NIEM-2.1_6-41_REF_SUB_EXT: xsd:import
attribute schemaLocation required. |
Within the schema, the element
xsd:import MUST carry the attribute schemaLocation. |
| Auto Pass |
0 |
NIEM-2.1_6-42_REF_SUB_EXT:
schemaLocation must be an absolute-URI or a relative-path reference as
defined by [RFC3986]. |
Within the schema, the value of
the required attribute schemaLocation carried by the element xsd:import
MUST match either the production <absolute-URI> or the definition of
"relative-path reference," as defined by [RFC3986]. |
| Auto Pass |
0 |
NIEM-2.1_6-43_REF_SUB_EXT:
schemaLocations of imports must resolve. |
Within the schema, the value of
the required attribute schemaLocation carried by the element xsd:import
MUST be resolvable to an XML schema document file that is valid according
to [XMLSchemaStructures] and [XMLSchemaDatatypes]. |
| Auto Pass |
0 |
NIEM-2.1_6-44_REF_SUB_EXT: Namespaces
other than the XML namespace or XML Schema namespace must be imported. |
Within the schema, when a
namespace other than the XML namespace or the XML Schema namespace is
used, it MUST be imported into the schema using the xsd:import element.
|
| Manual Fail |
0 |
NIEM-2.1_6-45_REF_SUB_EXT: |
Within the schema, when a
namespace other than the XML namespace or the XML Schema namespace is
used, its content MUST be valid with respect to the schema imported for
that namespace. |
| Auto Pass |
0 |
NIEM-2.1_6-46_REF_EXT: One annotation
only |
Within the schema, an element
SHALL have at most one instance of an element xsd:annotation as an
immediate child. |
| Manual Fail |
0 |
NIEM-2.1_6-47_REF_EXT: Human-Readable
Documentation |
Within the schema, the content
of the xsd:documentation element that constitutes the data definition of a
component MUST be character information items as specified by
[XMLInfoSet]. |
| Manual Fail |
0 |
NIEM-2.1_6-48_REF_SUB_EXT: |
XML comments SHALL not be used
for persistent information about constructs within the schema. |
| Manual Fail |
0 |
NIEM-2.1_6-49_REF_EXT: xsd:appinfo child
element must be EII or CII. |
Within the schema, any immediate
child of an xsd:appinfo element SHALL be an element information item or a
comment information item. |
| Auto Pass |
0 |
NIEM-2.1_6-50_REF_EXT: xsd:appinfo child
element must be in a namespace. |
Within the schema, any element
that is an immediate child of an xsd:appinfo element SHALL be in a
namespace. |
| Auto Pass |
0 |
NIEM-2.1_6-51_REF_EXT: xsd:appinfo
descendant cannot be from XML Schema namespace. |
Within the schema, an element in
the XML Schema namespace MUST NOT occur as a descendant of any element
xsd:appinfo. |
| Auto Pass |
0 |
NIEM-2.1_6-52_REF_SUB_EXT:
xsd:complexType children. |
Within the schema, the element
xsd:complexType MUST have as an immediate child either the element
xsd:complexContent or the element xsd:simpleContent. |
| Auto Pass |
0 |
NIEM-2.1_6-53_REF:
xsd:simpleContent immediate child. |
Within the schema, the element
xsd:simpleContent MUST have as an immediate child the element
xsd:extension. |
| Manual Fail |
0 |
NIEM-2.1_6-54_REF_SUB_EXT: simpleType
xsd:extension. |
Within the schema, given an
element xsd:simpleContent with a child xsd:extension owning an attribute
base, if the attribute base has a value that resolves to the name of a
simple type, then the element xsd:extension MUST have an immediate child
element xsd:attributeGroup. |
| Auto Pass |
0 |
NIEM-2.1_6-55_REF:
xsd:complexContent immediate child. |
Within the schema, the element
xsd:complexContent MUST have as an immediate child the element
xsd:extension. |
| Auto Pass |
0 |
NIEM-2.1_6-56_REF_SUB_EXT:
xsd:complexContent xsd:extension base attribute value. |
Within the schema, given an
element xsd:complexContent with a child xsd:extension owning an attribute
base, the attribute base MUST have a value that resolves to the name of
one of the following: 1. The type structures:ComplexObjectType. 2. The
type structures:MetadataType. 3. The type structures:AugmentationType. 4.
A complex type that is a NIEM-conformant component. |
| Auto Pass |
0 |
NIEM-2.1_6-57_EXT:
xsd:complexContent xsd:restriction base attribute value. |
Within the schema, given an
element xsd:complexContent with a child xsd:restriction owning an
attribute base, the attribute base MUST have a value that resolves to the
name of a complex type that is a NIEM-conformant component. |
| Auto Pass |
0 |
NIEM-2.1_6-58_REF_SUB_EXT:
xsd:attributeGroup ref attribute. |
Within the schema, any
occurrence of the element xsd:attributeGroup MUST own an attribute ref.
|
| Auto Pass |
0 |
NIEM-2.1_6-59_REF_SUB_EXT:
xsd:attributeGroup ref value. |
Within the schema, the attribute
ref owned by any element xsd:attributeGroup MUST have a value of a
qualified name (possibly using the default namespace) that SHALL resolve
to the namespace for the NIEM structures namespace and the local name
SimpleObjectAttributeGroup. |
| Auto Pass |
0 |
NIEM-2.1_7-01_REF_EXT: |
Within the schema, the document
element xsd:schema MUST have application information
appinfo:ConformantIndicator, with text content "true". |
| Manual Fail |
0 |
NIEM-2.1_7-02_REF_SUB_EXT_CON: |
Two XML Schema documents SHALL
have the same value for attribute targetNamespace carried by the element
xsd:schema, if and only if they represent the same set of components.
|
| Manual Fail |
0 |
NIEM-2.1_7-03_REF_SUB_EXT_CON: |
Two XML Schema documents SHALL
have the same value for attribute targetNamespace carried by the element
xsd:schema, and different values for attribute version carried by the
element xsd:schema if and only if they are different views of the same set
of components. |
| Auto Pass |
0 |
NIEM-2.1_7-04_REF_EXT: xsd:complexType
documentation. |
Within the schema, any element
xsd:complexType MUST be a documented component. |
| Auto Pass |
0 |
NIEM-2.1_7-05_REF_EXT: xsd:simpleType
documentation. |
Within the schema, any element
xsd:simpleType MUST be a documented component. |
| Auto Pass |
0 |
NIEM-2.1_7-06_REF_EXT: xsd:element
documentation. |
Within the schema, any element
xsd:element that is an immediate child of an element xsd:schema MUST be a
documented component. |
| Auto Pass |
0 |
NIEM-2.1_7-07_REF_EXT: xsd:attribute
documentation. |
Within the schema, any element
xsd:attribute that is an immediate child of an element xsd:schema MUST be
a documented component. |
| Auto Pass |
0 |
NIEM-2.1_7-08_REF_EXT: xsd:enumeration
documentation. |
Within the schema, any element
xsd:enumeration MUST be a documented component. |
| Auto Pass |
0 |
NIEM-2.1_7-09_REF_EXT: xsd:schema
documentation. |
Within the schema, the document
element xsd:schema MUST be a documented component. |
| Manual Fail |
0 |
NIEM-2.1_7-10_REF_EXT: data element
definition. |
Words or synonyms for the words
within a data element definition SHALL NOT be reused as terms in the
corresponding component name if those words dilute the semantics and
understanding of, or impart ambiguity to, the entity or concept that the
component represents. |
| Manual Fail |
0 |
NIEM-2.1_7-11_REF_EXT: object semantic
meaning. |
An object class SHALL have one
and only one associated semantic meaning (i.e., a single word sense) as
described in the definition of the component that represents that object
class. |
| Manual Fail |
0 |
NIEM-2.1_7-12_REF_EXT: object
definition. |
An object class SHALL NOT be
redefined within the definitions of the components that represent
properties or subparts of that entity or class. |
| Manual Fail |
0 |
NIEM-2.1_7-13_REF_EXT: data
definition. |
A data definition SHALL NOT
contain explicit representational or data typing information such as
number characters, type of characters, etc., unless the very nature of the
component can be described only by such information. |
| Manual Fail |
0 |
NIEM-2.1_7-14_REF_EXT: Standard Opening
Phrases |
A component definition SHALL
begin with a standard opening phrase that depends on the class of the
component per Table 7-2: Standard Opening Phrases. |
| Auto Pass |
0 |
NIEM-2.1_7-15_REF_EXT: appinfo namespace
must be imported. |
The schema SHALL import the
appinfo namespace. |
| Manual Fail |
0 |
NIEM-2.1_7-16_REF_EXT: deprecated
components. |
A component that is deprecated
SHALL be indicated as such by the component having application information
appinfo:Deprecated, with an attribute value with a value of true. |
| Auto Pass |
0 |
NIEM-2.1_7-17_REF_EXT: appinfo:Base
usage. |
Within the schema, the element
appinfo:Base MAY be used in one of the following ways: 1. By a type
definition, to indicate the base type, or structures:Object or
structures:Association. 2. By an element declaration, to indicate the base
element. The element appinfo:Base SHALL NOT be used for any other purpose.
|
| Auto Pass |
0 |
NIEM-2.1_7-18_REF_EXT: |
Within the schema, the element
appinfo:Base SHALL indicate, by namespace and name, one of the following:
1. A NIEM-conformant schema component. 2. structures:Object. 3.
structures:Association. |
| Auto Pass |
0 |
NIEM-2.1_7-19_REF_EXT: appinfo:Base
appinfo:namespace attribute value. |
Within the schema, an attribute
appinfo:namespace owned by an element appinfo:Base SHALL have a value of
either of the following: 1. A namespace which is the target namespace of a
NIEM-conformant schema. 2. The structures namespace. |
| Auto Pass |
0 |
NIEM-2.1_7-20_REF_EXT: appinfo:Base with
no appinfo:namespace attribute. |
Within the schema, an element
appinfo:Base that does not own an attribute appinfo:namespace SHALL refer
to the target namespace of the schema in which it is used. |
| Auto Pass |
0 |
NIEM-2.1_7-21_REF_EXT: appinfo:Base must
have appinfo:name. |
Within the schema, an element
appinfo:Base SHALL own an attribute appinfo:name. |
| Auto Pass |
0 |
NIEM-2.1_7-22_REF_EXT: appinfo:name value
for NIEM-conformant namespace in appinfo:Base. |
Within the schema, if an element
appinfo:Base references a NIEM-conformant namespace, then the value of the
attribute appinfo:name owned by the element appinfo:Base SHALL indicate a
schema component in the referenced namespace. |
| Auto Pass |
0 |
NIEM-2.1_7-23_REF_EXT: appinfo:name value
for structures namespace in appinfo:Base |
Within the schema, if an element
appinfo:Base indicates the structures namespace, then the value of the
attribute appinfo:name owned by the element appinfo:Base SHALL have a
value of one of the following: 1. structures:Object. 2.
structures:Association. 3. A schema component defined by the structures
schema. |
| Auto Pass |
0 |
NIEM-2.1_7-24_REF_EXT: appinfo:AppliesTo
usage. |
Within the schema, the element
appinfo:AppliesTo MAY be used in any of the following ways: 1. To indicate
a base type to which an augmentation may be applied. 2. To indicate a base
type to which a metadata type may be applied. The element
appinfo:AppliesTo SHALL NOT be used for any other purpose. |
| Auto Pass |
0 |
NIEM-2.1_7-25_REF_EXT: appinfo:AppliesTo
must have namespace and name. |
Within the schema, the element
appinfo:AppliesTo SHALL indicate a schema component by namespace and name.
|
| Auto Pass |
0 |
NIEM-2.1_7-26_REF_EXT: appinfo:namespace
must indicate the namespace of the type referenced by
appinfo:AppliesTo. |
Within the schema, an attribute
appinfo:namespace owned by an element appinfo:AppliesTo SHALL indicate the
namespace of the type to which appinfo:AppliesTo refers. The indicated
namespace SHALL be defined by a NIEM-conformant schema. |
| Auto Pass |
0 |
NIEM-2.1_7-27_REF_EXT: appinfo:AppliesTo
applicability. |
Given that the element
appinfo:AppliesTo refers to a type, the applicability described by the
element SHALL be understood to be the indicated type or a type
transitively derived from the indicated type. |
| Auto Pass |
0 |
NIEM-2.1_7-28_REF_EXT: appinfo:AppliesTo
without appinfo:namespace. |
Within the schema, an element
appinfo:AppliesTo that does not carry an attribute appinfo:namespace SHALL
refer to the target namespace of the schema in which it is used. |
| Auto Pass |
0 |
NIEM-2.1_7-29_REF_EXT: appinfo:AppliesTo
must have appinfo:name. |
Within the schema, an element
appinfo:AppliesTo SHALL carry an attribute appinfo:name. The value of this
attribute SHALL indicate the local name of a schema component within the
namespace specified by the element. |
| Manual Fail |
0 |
NIEM-2.1_7-30_REF_EXT:
appinfo:ReferenceTarget must contain a valid type. |
Within the schema, the element
appinfo:ReferenceTarget SHALL identify the XML Schema type definition of
an element information item to which an instance of a reference element
may validly refer. The element appinfo:ReferenceTarget SHALL NOT be used
for any other purpose. |
| Auto Pass |
0 |
NIEM-2.1_7-31_REF_EXT: A reference
element must have at most one instance of appinfo:ReferenceTarget |
Within the schema, a reference
element MUST have at most one instance of the element
appinfo:ReferenceTarget. |
| Auto Pass |
0 |
NIEM-2.1_7-32_REF_EXT:
appinfo:ReferenceTarget must indicate a type definition schema component,
by namespace and name. |
Within the schema, the element
appinfo:ReferenceTarget SHALL indicate a type definition schema component,
by namespace and name. |
| Manual Fail |
0 |
NIEM-2.1_7-33_REF_EXT:
appinfo:ReferenceTarget appinfo:namespace reference. |
Within the schema, an attribute
appinfo:namespace carried by an element appinfo:ReferenceTarget SHALL
indicate the namespace of the referenced schema component. The indicated
namespace SHALL be defined by a reference or extension schema. |
| Auto Pass |
0 |
NIEM-2.1_7-34_REF_EXT:
appinfo:ReferenceTarget with no appinfo:namespace. |
Within the schema, an element
appinfo:ReferenceTarget that does not carry an attribute appinfo:namespace
SHALL refer to the target namespace of the schema in which it is used.
|
| Auto Pass |
0 |
NIEM-2.1_7-35_REF_EXT:
appinfo:ReferenceTarget appinfo:name value. |
Within the schema, an element
appinfo:ReferenceTarget SHALL carry an attribute appinfo:name. The value
of this attribute SHALL indicate the local name of a type definition
schema component within the namespace specified by the element. |
| Manual Fail |
0 |
NIEM-2.1_7-36_REF_SUB_EXT: Simple
type metadata and properties. |
Within the schema, a simple type
definition that uses xsd:list SHOULD NOT be defined if any member of the
list requires a property or metadata that is different than other members
of the list. All members of the list SHOULD have the same metadata, and
should be related via the same properties. |
| Manual Fail |
0 |
NIEM-2.1_7-37_REF_SUB_EXT:
ComplexType definition. |
Within the schema, a complex
type definition SHALL be one of the following classes of types: 1. An
object type. 2. A role type. 3. An association type. 4. A metadata type.
5. An augmentation type. 6. An adapter type. |
| Manual Fail |
0 |
NIEM-2.1_7-38_REF_SUB_EXT: An element
must not be introduced more than once into the direct content of a type
definition. |
Within the schema, an element
MUST NOT be introduced more than once into the direct content of a type
definition. This applies to content acquired through extension of base
types. This does not apply to a base element or derived element to one
previously existing in the type definition. |
| Manual Fail |
0 |
NIEM-2.1_7-39_REF_EXT: ComplexType
definition. |
Within the schema, an object
type SHALL be a complex type definition that either constitutes a
NIEM-conformant component or for which there exists a NIEM-conformant
component of one of the following forms: 1. Has simple content, is based
on a simple type, and contains the attribute group
structures:SimpleObjectAttributeGroup, and has application information
appinfo:Base of structures:Object. 2. Has complex content, and is based on
complex type structures:ComplexObjectType, and has application information
appinfo:Base of structures:Object. 3. Is a complex type that is derived
from an object type, which is defined according to this rule. |
| Manual Fail |
0 |
NIEM-2.1_7-40_REF_SUB_EXT: RoleOf
elements. |
Within the schema, any element
with a name beginning with the string RoleOf SHALL represent a base type,
of which the containing type represents a role. |
| Manual Fail |
0 |
NIEM-2.1_7-41_REF_EXT: Association
complex type definition. |
Within the schema, an
association type SHALL be a complex type definition that either
constitutes a NIEM-conformant component or for which there exists a
NIEM-conformant component definition. The NIEM-conformant component
definition SHALL have one of the following forms: 1. Has complex content,
is based on the complex type structures:ComplexObjectType, and has
application information appinfo:Base of structures:Association. 2. Is a
complex type that is derived from an association type, which is defined
according to this rule. |
| Manual Fail |
0 |
NIEM-2.1_7-42_REF_SUB_EXT:
association type reference elements. |
Given that an association type
defines a relationship between a set of participants, within an
association type definition, any element that represents a participant
SHALL be a reference element. |
| Manual Fail |
0 |
NIEM-2.1_7-43_REF_SUB_EXT: metadata
type elements. |
Within the schema, a metadata
type SHALL contain elements appropriate for a specific class of data about
data. |
| Auto Pass |
0 |
NIEM-2.1_7-44_REF_SUB_EXT: metadata
type derivation. |
Within the schema, a metadata
type and only a metadata type SHALL be derived directly from
structures:MetadataType. |
| Auto Pass |
0 |
NIEM-2.1_7-45_REF_EXT: metadata
application information. |
Within the schema, a metadata
type MAY have application information appinfo:AppliesTo, indicating the
NIEM-conformant object, association, or external adapter types to which
the metadata applies. |
| Auto Pass |
0 |
NIEM-2.1_7-46_REF_EXT: metadata with no
application information. |
Within the schema, a metadata
type that does not have application information appinfo:AppliesTo MAY be
applied to any object type, association type, or external adapter type.
|
| Manual Fail |
0 |
NIEM-2.1_7-47_REF_SUB_EXT:
Augmentation Type. |
An augmentation type: 1. SHALL
be transitively derived from structures:AugmentationType. 2. SHALL contain
elements that represent properties to be applied to a base type. |
| Auto Pass |
0 |
NIEM-2.1_7-48_REF_SUB_EXT:
Augmentation element definition. |
Within the schema, an
augmentation element definition: 1. SHALL have a type that is an
augmentation type. 2. SHALL use the substitutionGroup attribute such that
it is transitively substitutable for the element structures:Augmentation.
An element that is not an augmentation element SHALL NOT meet either of
the above criteria. |
| Auto Pass |
0 |
NIEM-2.1_7-49_REF_EXT: Element definition
structures:AppliesTo. |
Within the schema, an element
definition for an augmentation element MAY contain one or more instances
of the element structures:AppliesTo as application information to specify
types to which the augmentation element applies. |
| Auto Pass |
0 |
NIEM-2.1_7-50_REF_EXT: Element definition
for augmentation element with no structures:AppliesTo instances. |
Within the schema, an element
definition for an augmentation element that does not contain any instances
of the element structures:AppliesTo MAY be applied to any object or
association type. |
| Manual Fail |
0 |
NIEM-2.1_7-51_REF_SUB_EXT: Component
type definition references. |
Any type definition referenced
by a component within the schema MUST be from one of the following: 1. The
schema being defined. 2. A namespace imported as NIEM-conformant. 3. The
XML Schema namespace. 4. The structures namespace. |
| Manual Fail |
0 |
NIEM-2.1_7-52_REF_SUB_EXT: Component
element declaration references. |
Any element declaration
referenced by a component within the schema MUST be from one of the
following: 1. The schema being defined. 2. A namespace imported as
NIEM-conformant. 3. The structures namespace. 4. An external namespace, in
accordance with the rules for external schemas as specified by this
specification. |
| Manual Fail |
0 |
NIEM-2.1_7-53_REF_SUB_EXT: Componenet
attribute declaration references. |
Any attribute declaration
referenced by a component within the schema MUST be from one of the
following: 1. The schema being defined. 2. A namespace imported as
NIEM-conformant. 3. The structures namespace. 4. The XML namespace. 5. An
external namespace, in accordance with the rules for external schemas as
specified by this specification. |
| Auto Pass |
0 |
NIEM-2.1_7-54_REF_EXT: NIEM structures
namespace must be imported. |
The schema MUST import the NIEM
structures namespace. |
| Manual Fail |
0 |
NIEM-2.1_7-55_REF_SUB_EXT_INS:
Schema must use content within the NDR strucures namespace as
specified. |
The schema or instance MUST use
content within the NIEM structures namespace as specified in this document
and ONLY as specified by this document. |
| Manual Fail |
0 |
NIEM-2.1_7-56_REF_SUB_EXT:
ComplexType definition structures:sequenceID. |
Within the schema, a complex
type definition SHALL include the attribute structures:sequenceID if the
order of an occurrence of the type, within its parent, relative to its
siblings, is meaningful and pertinent and if the schema does not specify
the desired sequential order. |
| Manual Fail |
0 |
NIEM-2.1_7-57_REF_SUB_EXT: Reference
elements. |
Within the schema, a reference
element and only a reference element SHALL be defined to be of type
structures:ReferenceType. |
| Auto Pass |
0 |
NIEM-2.1_7-58_REF_SUB_EXT:
ComplexType must not own the attribute structures:ref. |
Within the schema, a complex
type SHALL NOT be defined such that an instance of that type owns the
attribute structures:ref. |
| Manual Fail |
0 |
NIEM-2.1_7-59_REF_SUB_EXT: NCName and
NCNameReference Elements. |
Within the schema, any two
elements of the form NCName and NCNameReference where the string value of
NCName is the same in both forms, SHALL be defined to have identical
semantics. NIEM recognizes no difference in meaning between a reference
element and an element that is not a reference element. |
| Manual Fail |
0 |
NIEM-2.1_7-60_REF_EXT:
appinfo:ReferenceTarget for NCNameReference. |
Within the schema, if both
elements NCName and NCNameReference exist, then the
appinfo:ReferenceTarget of any NCNameReference element MUST be the type of
the element NCName. |
| Auto Pass |
0 |
NIEM-2.1_7-61_REF_EXT:
appinfo:ConformantIndicator. |
Within the schema, an element
xsd:import that imports a namespace defined by an external schema MUST
have the application information appinfo:ConformantIndicator, with a value
of false. |
| Auto Pass |
0 |
NIEM-2.1_7-62_REF_EXT: xsd:import for and
external schema. |
Within the schema, an element
xsd:import that imports a namespace defined by an external schema MUST be
a documented component. |
| Manual Fail |
0 |
NIEM-2.1_7-63_REF_EXT: AdapterType
application information. |
Within the schema, an adapter
type MUST have application information
appinfo:ExternalAdapterTypeIndicator with a value of true. A type that is
not an adapter type SHALL NOT contain that indicator. |
| Auto Pass |
0 |
NIEM-2.1_7-64_REF_SUB_EXT:
AdapterType must be an immediate extension of
structures:ComplexObjectType. |
Within the schema, an adapter
type MUST be an immediate extension of type structures:ComplexObjectType.
|
| Manual Fail |
0 |
NIEM-2.1_7-65_REF_SUB_EXT:
AdapterType composition. |
Within the schema, an adapter
type MUST be composed of only elements and attributes from an external
standard. |
| Auto Pass |
0 |
NIEM-2.1_7-66_REF_EXT: AdapterType
element reference. |
Within the schema, an element
reference used in an adapter type definition MUST be a documented
component. |
| Auto Pass |
0 |
NIEM-2.1_7-67_REF_EXT: AdapterType
attribute reference. |
Within the schema, an attribute
reference used in an adapter type definition MUST be a documented
component. |
| Auto Pass |
0 |
NIEM-2.1_7-68_REF_SUB_EXT:
AdapterType must not be extended or restricted. |
Within the schema, an adapter
type MUST NOT be extended or restricted. |
| Manual Fail |
0 |
NIEM-2.1_7-69_SUB:
targetNamespace attribute value. |
The value of the targetNamespace
attribute owned by the xsd:schema document element of the subset schema
must be the same as the value of the targetNamespace attribute owned by
the xsd:schema document element of the reference schema. |
| Manual Fail |
0 |
NIEM-2.1_7-70_SUB:
Schema construction. |
The schema must be constructed
such that any instance that is XML Schema valid against the schema must
also be XML Schema valid against the base schema. |
| Manual Fail |
0 |
NIEM-2.1_8-01_INS:
XML document must be schema-valid. |
The XML document MUST be
schema-valid, assessed with reference to the schema composed of the
reference schemas, extension schemas, exchange schemas, utility schemas,
and external schemas for the relevant namespaces. |
| Auto Pass |
0 |
NIEM-2.1_8-02_INS:
Elements with no content. |
Within the instance, the meaning
of an element with no content is that additional properties are not
asserted. There SHALL NOT be additional meaning interpreted for an element
with no content. |
| Auto Pass |
0 |
NIEM-2.1_8-03_INS:
Property assertion. |
Within an element instance,
there SHALL NOT be any difference in meaning between a property asserted
via element containment and a property asserted by element reference,
except as explicitly described by the semantics of the elements involved.
|
| Manual Fail |
0 |
NIEM-2.1_8-04_INS:
ID attribute value |
Given that the IDREF that is the
value of an attribute structures:ref matches the value of an ID attribute
on some element in the XML document, that ID attribute must be an
occurrence of the attribute structures:id. |
| Manual Fail |
0 |
NIEM-2.1_8-05_INS:
attribute structures:ref reference. |
Within an element instance,
given that a reference element is restricted to a target type T, any
attribute structures:ref MUST reference an element that has a type
definition of type T or that is derived from type T. |
| Auto Pass |
0 |
NIEM-2.1_8-06_INS:
child element order. |
The order of elements that are
children of an element SHALL be presented as if their sequential order is
as follows: 1. First, elements owning an attribute structures:sequenceID,
in the order that would be yielded with their sequence IDs sorted via sort
element as defined by [XSLT], with a data type of number and an order of
ascending. 2. Following those elements, the remaining elements, in the
order in which they occur within the XML instance. |
| Manual Fail |
0 |
NIEM-2.1_8-07_REF_EXT_INS:
structures:sequenceID interpretation. |
Within a schema or instance, the
attribute structures:sequenceID SHALL NOT be interpreted as meaningful
beyond an indicator of sequential order of an object relative to its
siblings. |
| Manual Fail |
0 |
NIEM-2.1_8-08_INS:
Object metadata. |
Within an element instance, when
an object O links to a metadata object via an attribute
structures:metadata, the information in the metadata object SHALL be
applied to the object O. |
| Manual Fail |
0 |
NIEM-2.1_8-09_INS:
Element relationship metadata. |
Within an element instance, when
an object O1 contains an element E, with content object O2 or with a
reference to object O2, and O2 links to a metadata object via an attribute
structures:linkMetadata, the information in the metadata object SHALL be
applied to the relationship E between O1 and O2. |
| Manual Fail |
0 |
NIEM-2.1_8-10_INS:
ID attribute must be an occurrence of the attribute structures:id. |
Given that each IDREF in the
value of an attribute structures:metadata must match the value of an ID
attribute on some element in the XML document, that ID attribute MUST be
an occurrence of the attribute structures:id. |
| Manual Fail |
0 |
NIEM-2.1_8-11_INS:
Elements refrenced by structures:metadata must have a type definition that
is derived from structures:MetadataType. |
Each element that an attribute
structures:metadata references MUST have a type definition that is derived
from structures:MetadataType. |
| Manual Fail |
0 |
NIEM-2.1_8-12_INS:
ID attribute must be an occurrence of the attribute structures:id. |
Given that each IDREF in the
value of an attribute structures:linkMetadata must match the value of an
ID attribute on some element in the XML document, that ID attribute MUST
be an occurrence of the attribute structures:id. |
| Manual Fail |
0 |
NIEM-2.1_8-13_INS:
Attributes refrenced by structures:metadata must have a type definition
that is derived from structures:MetadataType. |
Each element that an attribute
structures:linkMetadata references MUST have a type definition that is
derived from structures:MetadataType. |
| Manual Fail |
0 |
NIEM-2.1_8-14_INS:
element information item and type definition relationship. |
Given that an element
information item E has a type definition of some type T, each metadata
type that is the type definition of an element information item referenced
by an attribute structures:metadata or structures:linkMetadata on element
E MUST be applicable to T. |
| Auto Pass |
0 |
NIEM-2.1_9-01_REF_SUB_EXT:
complexType name and XML Schema namespace simpleType extension. |
Within the schema, a complex
type that is a direct extension of a simple type from the XML Schema
namespace simple type MAY use the same local name as the simple type if
and only if the extension adds no content other than the attribute group
structures:SimpleObjectAttributeGroup. |
| Manual Fail |
0 |
NIEM-2.1_9-02_REF_SUB_EXT: XML Schema
component name must be English. |
The name of any XML Schema
component defined by the schema SHALL be composed of words from the
English language, using the prevalent U.S. spelling, as provided by [OED].
|
| Auto Pass |
0 |
NIEM-2.1_9-03_REF_SUB_EXT: XML Schema
component name |
The name of any XML Schema
component defined by the schema SHALL contain only the following
characters: *Upper-case letters ('A'-'Z'). *Lower-case letters ('a'-'z').
*Digits ('0'-'9'). *Hyphen ('-'). Other characters, underscore ('_')
character and the period ('.') character SHALL NOT appear in component
names in NIEM-conformant schemas. |
| Manual Fail |
0 |
NIEM-2.1_9-04_REF_SUB_EXT: Component
name hyphen characters. |
The hyphen character ('-') MAY
appear in component names only when used as a separator between parts of a
single word, phrase, or value, which would otherwise be incomprehensible
without the use of a separator. |
| Auto Pass |
0 |
NIEM-2.1_9-05_REF_SUB_EXT: attribute
declaration names must being with a lower-case letter. |
Within the schema, any attribute
declaration SHALL have a name that begins with a lower-case letter
('a'-'z'). |
| Auto Pass |
0 |
NIEM-2.1_9-06_REF_SUB_EXT: XML Schema
components other that an attribute declaration must beging with an
upper-case letter. |
Within the schema, any XML
Schema component other than an attribute declaration SHALL have a name
that begins with an upper-case letter ('A'-'Z'). |
| Manual Fail |
0 |
NIEM-2.1_9-07_REF_SUB_EXT: XML Schema
component name shall use camel case. |
The name of any XML Schema
component defined by the schema SHALL use the camel case formatting
convention. |
| Manual Fail |
0 |
NIEM-2.1_9-08_REF_SUB_EXT: Schema
MUST consistently use approved acronyms, abbreviations, and word
truncations within defined names |
The schema MUST consistently use
approved acronyms, abbreviations, and word truncations within defined
names. The approved shortened forms are defined in Table 9-1 Abbreviations
Used in NIEM Names. |
| Manual Fail |
0 |
NIEM-2.1_9-09_REF_SUB_EXT: Noun use
in XML Schema component names. |
A noun used as a term in the
name of an XML Schema component MUST be in singular form unless the
concept itself is plural. |
| Manual Fail |
0 |
NIEM-2.1_9-10_REF_SUB_EXT: Verb use
in XML Schema component names. |
A verb used as a term in the
name of an XML Schema component MUST be used in the present tense unless
the concept itself is past tense. |
| Manual Fail |
0 |
NIEM-2.1_9-11_REF_SUB_EXT: Articles,
conjunctions, and prepositions must not be used in NDR component names. |
Articles, conjunctions, and
prepositions SHALL NOT be used in NIEM component names except where they
are required for clarity or by standard convention. |
| Manual Fail |
0 |
NIEM-2.1_9-12_REF_SUB_EXT: Element
and Attribute name format. |
Except as specified elsewhere in
this document, any element or attribute defined within the schema SHALL
have a name that takes the form: *Object-class qualifier terms (0 or
more). *An object class term (1). *Property qualifier terms (0 or more).
*A property term (1). *Representation qualifier terms (0 or more). *A
representation term (1). |
| Manual Fail |
0 |
NIEM-2.1_9-13_REF_SUB_EXT:
Object-class term of a NIEM component. |
The object-class term of a NIEM
component SHALL consist of a term identifying a category of concrete
concepts or entities. |
| Manual Fail |
0 |
NIEM-2.1_9-14_REF_SUB_EXT: Property
terms. |
A property term SHALL describe
or represent a characteristic or subpart of an entity or concept. |
| Auto Pass |
0 |
NIEM-2.1_9-15_REF_SUB_EXT: Multiple
qualifier terms with a component name. |
Multiple qualifier terms MAY be
used within a component name as necessary to ensure clarity and uniqueness
within its namespace and usage context. |
| Manual Fail |
0 |
NIEM-2.1_9-16_REF_SUB_EXT: Number of
qualifier terms should be limited. |
The number of qualifier terms
SHOULD be limited to the absolute minimum required to make the component
name unique and understandable. |
| Manual Fail |
0 |
NIEM-2.1_9-17_REF_SUB_EXT: Qualifier
order. |
The order of qualifiers SHALL
NOT be used to differentiate names. |
| Manual Fail |
0 |
NIEM-2.1_9-18_REF_EXT: Representation
term and Property term redundancy. |
If any word in the
representation term is redundant with any word in the property term, one
occurrence SHOULD be deleted. |
| Auto Pass |
0 |
NIEM-2.1_9-19_REF_SUB_EXT: Simple
Content element declaration name. |
Within the schema, the name of
an element declaration that is of simple content MUST use a representation
term found in Table 9-2: Representation Terms. |
| Manual Fail |
0 |
NIEM-2.1_9-20_REF_SUB_EXT: Complex
Content element declaration names in Table 9-2. |
Within the schema, the name of
an element declaration that is of complex content, and that corresponds to
a concept listed in Table 9-2: Representation Terms, MUST use a
representation term from that table. |
| Manual Fail |
0 |
NIEM-2.1_9-21_REF_SUB_EXT: Complex
Content element declaration names in Table 9-2. |
Within the schema, the name of
an element declaration that is of complex content and that does not
correspond to a concept listed in Table 9-2: Representation Terms MUST NOT
use a representation term. |
| Manual Fail |
0 |
NIEM-2.1_9-22_REF_SUB_EXT: Complex
Content element declaration names not in Table 9-2 |
Within the schema, the name of
an attribute declaration MUST use a representation term from Table 9-2:
Representation Terms. |
| Auto Pass |
0 |
NIEM-2.1_9-23_REF_SUB_EXT: Type
definition must use the representation term Type. |
Within the schema, the name of
any type definition MUST use the representation term Type. |
| Auto Pass |
0 |
NIEM-2.1_9-24_REF_SUB_EXT: simpleType
name must use the qualifier Simple. |
Within the schema, the name of
any simple type definition SHALL use the representation term qualifier
Simple. This qualifier SHALL appear after any other representation term
qualifiers. |
| Auto Pass |
0 |
NIEM-2.1_9-25_REF_SUB_EXT: Any code
type shall use the representation term qualifier Code. |
Within the schema, the name of
any code type SHALL use the representation term qualifier Code. |
| Auto Pass |
0 |
NIEM-2.1_9-26_REF_SUB_EXT: Types with
base type definitions or tranitively based on a code types must use the
term qualifier Code. |
Within the schema, any type
definition which has a base type definition of a code type or which is
transitively based on a code type SHALL have a name that uses the
representation term qualifier Code. |
| Manual Fail |
0 |
NIEM-2.1_9-27_REF_SUB_EXT:
Association types shall have a name that uses the representation term
qualifier Association. |
Within the schema, any
association type SHALL have a name that uses the representation term
qualifier Association. Types other than association types SHALL NOT use
the representation term qualifier Association. |
| Auto Pass |
0 |
NIEM-2.1_9-28_REF_SUB_EXT:
AugmentationType must use the qualifier Augmentation. |
Within the schema, any
augmentation type SHALL have a name that uses the representation term
qualifier Augmentation. Types other than augmentation types SHALL NOT use
the representation term qualifier Augmentation. |
| Auto Pass |
0 |
NIEM-2.1_9-29_REF_SUB_EXT: Metadata
types must use the qualifier Metadata. |
Within the schema, any metadata
type SHALL have a name that uses the representation term qualifier
Metadata. Types other than metadata types SHALL NOT use the representation
term qualifier Metadata. |
| Auto Pass |
0 |
NIEM-2.1_9-30_REF_SUB_EXT: Attribute
group definitions must use the qualifier AttributeGroup. |
Within the schema, the name of
any attribute group definition schema component SHALL use the
representation term AttributeGroup. |
| Auto Pass |
0 |
NIEM-2.1_9-31_REF_SUB_EXT: Reference
element must use suffix Reference. |
Within the schema, the name of
any reference element SHALL use the representation term suffix Reference.
|
| Auto Pass |
0 |
NIEM-2.1_9-32_REF_SUB_EXT:
Association elements must use the qualifier Association. |
Within the schema, the name of
an association element SHALL use the representation term qualifier
Association. |
| Auto Pass |
0 |
NIEM-2.1_9-33_REF_SUB_EXT:
Augmentation elements must use the qualifier Augmentation. |
Within the schema, the name of
an augmentation element SHALL use the representation term Augmentation.
|
| Auto Pass |
0 |
NIEM-2.1_9-34_REF_SUB_EXT: Metadata
elements must use the term Metadata. |
Within the schema, the name of a
metadata element SHALL use the representation term Metadata. |
| Auto Pass |
0 |
NIEM-2.1_9-35_REF_SUB_EXT: Roles must
use the property term RoleOf. |
Within the schema, the name of a
role SHALL use the property term RoleOf. |